-
Notifications
You must be signed in to change notification settings - Fork 807
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Multi-Attach for io2 block devices #1799
Feature: Multi-Attach for io2 block devices #1799
Conversation
f109d19
to
5918d0b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need some static provisioning test cases.
- If multi-attach is not enabled on an existing volume, obviously mult-attach should fail. So we should have an expected-fail test.
- For this release, I believe that we are only intending to support multi-attach in dynamically provisioned volumes. If that's true, then we should enforce that, and have a test for that enforcement. If we decide that we'll handle the case where a statically provisioned volume has multi-attach enabled, then we should have an expected-success test for that.
@wmesard: changing LGTM is restricted to collaborators In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
337e89a
to
b84d4ec
Compare
0eb06fe
to
222c4c3
Compare
CI is green and this PR is now ready for another round in the ring : ) |
222c4c3
to
9ea4083
Compare
24a8e7b
to
bddbe0b
Compare
@wmesard: changing LGTM is restricted to collaborators In response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
9ea4083
to
a118ac8
Compare
Signed-off-by: Eddie Torres <[email protected]>
a118ac8
to
76a68ba
Compare
/lgtm |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: torredil The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Reference: kubernetes-sigs/aws-ebs-csi-driver#1799 Signed-off-by: Arnon Gilboa <[email protected]>
Reference: kubernetes-sigs/aws-ebs-csi-driver#1799 Signed-off-by: Arnon Gilboa <[email protected]>
Reference: kubernetes-sigs/aws-ebs-csi-driver#1799 Signed-off-by: Arnon Gilboa <[email protected]>
Reference: kubernetes-sigs/aws-ebs-csi-driver#1799 Signed-off-by: Arnon Gilboa <[email protected]> Co-authored-by: Arnon Gilboa <[email protected]>
Reference: kubernetes-sigs/aws-ebs-csi-driver#1799 Signed-off-by: Arnon Gilboa <[email protected]>
Reference: kubernetes-sigs/aws-ebs-csi-driver#1799 Signed-off-by: Arnon Gilboa <[email protected]>
Reference: kubernetes-sigs/aws-ebs-csi-driver#1799 Signed-off-by: Arnon Gilboa <[email protected]> Co-authored-by: Arnon Gilboa <[email protected]>
Reference: kubernetes-sigs/aws-ebs-csi-driver#1799 Signed-off-by: Arnon Gilboa <[email protected]> Co-authored-by: Arnon Gilboa <[email protected]>
Is this a bug fix or adding new feature?
What is this PR about? / Why do we need it?
This PR implements the ability to enable multi-attach for
io2
block devices by specifying theReadWriteMany
access mode inPersistentVolumeClaim.spec.accessModes
. A few important points to note:xfs
,ext3
,ext4
, andNTFS
aren't designed to be simultaneously accessed by multiple EC2 instances.See the documentation: https://github.com/torredil/aws-ebs-csi-driver/blob/d316ff830997cb38d17e38625cbaeea2e089068a/docs/multi-attach.md
What testing is done?
make test